Armin Ronacher breaks down two layers of agent loops: the internal cycle where a model calls tools and edits code, and the external harness that re-queues and re-runs tasks until a goal is met. He says loops shine for experiments, code ports, and security scans, but they generate brittle, over-defensive code and threaten human understanding, even as defenders must adopt loops to match automated attackers.

• Autonomous agent loops tend to produce defensive, bloated code—stacking fallbacks and exception-handling instead of fixing root design flaws.
• Loops work best on bounded, verifiable tasks like code ports (Zig-to-Rust, MiniJinja-to-Go), performance tuning, and security audits, where results can be mechanically checked or judged by a second LLM.
• For production or mission-critical systems, Ronacher still prefers deterministic, fully "peelable" code over the unpredictable, living-system feel of loop-generated software.
• Despite the risks, defenders may be forced to adopt loop-based approaches simply to keep pace with automated attackers using the same technique.